Method, system, and storage medium for implementing transaction-based data exchange

ABSTRACT

A method for implementing transaction-based data exchange. The method includes transferring information relating to a product via a transmission means selected by an individual at a computing device requesting the information. The information includes at least one of warranty information, accounting information, pricing information, and product details. The method further includes calculating a net worth relating to the product, and updating a financial application associated with the individual with results of the calculating.

BACKGROUND OF THE INVENTION

The invention relates generally to data processing, and moreparticularly, to a method, system, and storage medium for implementingtransaction-based data exchange.

Managing information can be a time consuming and often difficult task,particularly where large amounts of information are involved.Information can become outdated with the passage of time, change inresponse to new information or activities conducted, and may interrelatein important ways to other existing information in a manner that isundetected and unforeseen, causing it to be underutilized. One exampleis the purchase and sale of products. While a product purchased by anindividual may be subject to a warranty, the validity of that warrantymay be conditional upon the individual having the product serviced atspecified time periods throughout the warranty period (e.g., a warrantyfor rust protectant applied to a new vehicle). The individual may keeprecords of payments made (e.g., per an installment contract), as well asthe warranty paperwork, but unless the information concerning thewarranty conditions is well organized and efficiently managed, theindividual may neglect to service the product on time causing thewarranty to become invalid.

A variety of useful information is available or accessible regardingpurchases at the time of sale or pre-sale period. Productspecifications, pricing, taxes, manufacturer warranty registration andrebates, and other data may be helpful to a purchaser in makingpurchasing decisions, as well as long-term decisions related to thepurchase. Acquiring, organizing, and managing this information can bedifficult and time-consuming, partly because the information is notcentrally located but rather originates from various sources (e.g.,manufacturer, seller, financial institutions, etc.). What is needed,therefore, is a way to acquire, organize, and maintain transaction-basedinformation that is derived from a variety of disparate sources.

BRIEF SUMMARY OF THE INVENTION

Exemplary embodiments of the present invention include a method forimplementing transaction-based data exchange. The method includestransferring information relating to a product via a transmission meansselected by an individual at a computing device requesting theinformation. The information includes at least one of warrantyinformation, accounting information, pricing information, and productdetails. The method further includes calculating a net worth relating tothe product, and updating a financial application associated with theindividual with results of the calculating.

Additional exemplary embodiments include a system for implementingtransaction-based data exchange. The system includes a processorexecuting a data exchange system application and a link to at least oneclient system. The data exchange system application performs a method.The method includes transferring information relating to a product via atransmission means selected by an individual at the client devicerequesting the information. The information includes at least one ofwarranty information, accounting information, pricing information, andproduct details. The method further includes calculating a net worthrelating to the product and updating a financial application associatedwith the client device with results of the calculating.

Further exemplary embodiments include a storage medium for implementingtransaction-based data exchange. The storage medium is encoded withmachine-readable program code. The program code includes instructionsfor performing a method. The method includes transferring informationrelating to a product via a transmission means selected by an individualat a computing device requesting the information. The informationincludes at least one of warranty information, accounting information,pricing information, and product details. The method further includescalculating a net worth relating to the product, and updating afinancial application associated with the individual with results of thecalculating.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings wherein like elements are numbered alikein the several FIGURES:

FIG. 1 depicts a system upon which a data exchange system may beimplemented in exemplary embodiments;

FIG. 2 is a flow diagram of a process for acquiring and managing productinformation for use in implementing the data exchange system inexemplary embodiments;

FIG. 3 is a user interface screen illustrating sample product datamanaged by the data exchange system in exemplary embodiments;

FIG. 4 is a flow diagram of a process for acquiring and managingaccounting information via the data exchange system in exemplaryembodiments;

FIG. 5 is a user interface screen illustrating sample accounting datamanaged by the data exchange system in exemplary embodiments;

FIG. 6 is a flow diagram of a process for acquiring and managingwarranty information via the data exchange system in exemplaryembodiments;

FIG. 7 is a flow diagram of a process for acquiring and managing networth information via the data exchange system in exemplary embodiments;

FIG. 8 is a user interface screen illustrating sample net worth datamanaged by the data exchange system in exemplary embodiments;

FIGS. 9A and 9B are flowcharts illustrating how the process softwareimplementing the systems and methods of the invention may be integratedinto client, server, and network environments;

FIGS. 10A and 10B are flowcharts illustrating various ways in which theprocess software of the invention may be semi-automatically orautomatically deployed across various networks and onto server, client(user), and proxy computers;

FIGS. 11A through 11C are flowcharts illustrating how process softwarefor implementing the systems and methods of the invention are deployedthrough the installation and use of two different forms of a virtualprivate network (VPN); and

FIGS. 12A and 12B are flowcharts illustrating how the process softwarefor implementing the systems and methods of the invention can bedeployed through an On Demand business model, which allows the processsoftware to be shared and simultaneously service multiple customers in aflexible, automated fashion under a pay-for-what-you-use plan.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Exemplary embodiments of the present invention provide a variety ofuseful information regarding purchases at the point of sale or pre-saleperiod. Product specifications, pricing, taxes, manufacturer warrantyregistration and rebates, and other data are acquired from varioussources such as manufacturing enterprises, selling entities, financialinstitutions, etc. Embodiments of the invention acquire, organize, andfacilitate dissemination of this information on behalf of individualconsumers and/or businesses. Accounting information, warranties, and networth are some of the information that is managed by the invention. Thisinformation may be transferred to designated parties in several manners,including e.g., wireless transfer to a mobile computing device, viaemail, web access, etc.

Turning now to FIG. 1, an exemplary system upon which the data exchangeprocesses may be implemented will now be described. The exemplary system100 of FIG. 1 includes a host system 102, a selling entity 104, a smalloffice/home office (SOHO) client system 106, and manufacturing entities140, each of which may communicate with one another via one or morenetworks such as network 108.

Host system 102 may be a service provider that implements data exchangeactivities on behalf of entities such as one or more of manufacturingentities 140, selling entity 104, and SOHO client system 106 for a fee.The data exchange activities described herein may be implemented via anapplication 130 executing on host system 102. Host system 102 mayimplement one or more servers including a web server, applicationsserver, and database management server for conducting the data exchangeactivities described herein. Host system 102 may be an applicationservice provider (ASP), a financial institution (e.g., credit cardcompany, bank), or other similar type of service provider. Host system102 may be coupled to a data repository 131 that stores, e.g.,accounting rules and customer account records as described furtherherein.

Manufacturing entities 140 refer to enterprises that produce and sellgoods and/or services to purchasing entities. Manufacturing entities 140may also provide information relating to their products/services, suchas product specifications, product models, product images, suggestedretail pricing, manufacturer rebate information, and manufacturerwarranty information.

SOHO client system 106 refers to a computer device operated by anindividual in furtherance of a business purpose or a home informationmanagement objective (e.g., home inventory, financial account/assetmaintenance, etc.). SOHO client system 106 may comprise ageneral-purpose or laptop computer that executes one or moreapplications including, e.g., email client 128, web browser 129,financial accounting software 127, and other similar types of programs.In one embodiment, SOHO client 106 executes a Radio Frequency Identifier(RFID) reader 126 for scanning purchased products containing an RFID tagwith data exchange information provided therein. This is describedfurther herein.

In accordance with exemplary embodiments, selling entity 104 includes apoint-of-sale register 112 and products (e.g., product 122).Point-of-sale register 112 may comprise a processor-enabled device thatincludes software for implementing purchase transactions conductedtherein. Point-of-sale register 112 may also include memory for storingpurchase transaction information. In one embodiment, point-of-saleregister 112 includes an RFID reader (not shown) for scanning productspurchased and retrieving pricing information, as well as data exchangeinformation. Additionally, point-of-sale register 112 may be coupled toa network (e.g., network 108) for communicating with, e.g., host system102, a credit company, customer assistance client system 118, acorporate office of selling entity 104, etc.

In one embodiment, selling entity 104 includes a customer assistanceclient system 118 coupled to a data repository 120. Client system 118may be a general-purpose computer system operated by a frontdesk/customer service operator, or may be a freestanding, self-servicekiosk available for use by customers. Client system 118 may include anapplication for searching and retrieving product information (includingdata exchange information) stored in data repository 120. Further,client system 118 may execute in whole, or in part, the data exchangesystem application 130. For example, if the client system 118 is apersonal computer, the processing described herein may be shared by theclient system 118 and host system 102 (e.g., by providing an applet tothe client system 118).

In accordance with exemplary embodiments, data repository 120 storesproduct information in a product catalog including, e.g., productspecifications, product identification information, pricing, warrantyinformation, promotions and discounts, preferred customer pricing andservice information, etc. relating to the goods sold by selling entity104. While shown as separate devices, it will be understood by thoseskilled in the art that client system 118 and data repository 120 maycomprise a single device, whereby information is stored in memoryinternal to client system 118. Alternatively, client system 118 may bein communication with multiple data repositories located in variousgeographic locations (including data repository 120), which store theinformation described above with respect to data repository 120.

Selling entity 104 displays a variety of products for sale as istypically found in a retail (or wholesale) establishment. Products, suchas product 122 may include an RFID tag 124 which, when scanned bypoint-of-sale register 112, provides pricing information. In oneembodiment, RFID tag 124 may store additional information relating tothe product 122 such as manufacturer and/or store warranty information,discount information, manufacturer and/or store rebate information, etc.

A customer 115 is also shown in selling entity 104. Customer 115 maypossess a credit card/check card 114 and/or a smart card 116. Customer115 may also possess a mobile computing device 110 (e.g., personaldigital assistant, handheld device, cell phone, etc.). One or more ofcredit card/check card 114, smart card 116, and mobile computing device110 may be utilized in implementing the data exchange processes asdescribed further herein. It is assumed for purposes of illustrationthat the customer 115 is also the operator of SOHO client system 106.

The network 108 may be any type of known network including, but notlimited to, a wide area network (WAN), a local area network (LAN), aglobal network (e.g., Internet), a virtual private network (VPN), and anintranet. The network 108 may be implemented using a wireless network orany kind of physical network implementation known in the art. A usersystem (e.g., client system 106, client system 118, mobile computingdevice 110, point-of-sale register 112, manufacturing entities 140,etc.) may be coupled to the host system 102 through multiple networks(e.g., intranet and Internet) so that not all user systems are coupledto the host system 102 through the same network. One or more of the usersystems described above and the host system 102 may be connected to thenetwork 108 in a wireless fashion. In one embodiment, the network 108 isan intranet and one or more of the user systems execute a user interfaceapplication (e.g. a web browser) to contact the host system 102 throughthe network 108.

An exemplary embodiment for acquiring a variety of information fromvarious sources is performed via the data exchange system as describedin the flow diagram of FIG. 2. At step 202, the process is initiated byeither customer 115 or selling entity 104. For instance, client system118 may be available for searching and retrieving product informationfrom a product catalog or database in data repository 120. A prospectivecustomer (e.g., pre-sale customer) or current customer (post-salecustomer) may access client system 118 to determine if data exchangeservices are available for a product of interest. A pre-sale customermay desire discount and rebate information for a product of interest inorder to make an informed purchasing decision. A post-sale customer maydesire more detailed information regarding the product of interest.

At step 204, a search for the product of interest is conducted. If dataexchange activities are available for the product of interest, thecustomer 115 may request access to information available via the dataexchange system. This step is described further in FIGS. 4, 6, and 7.Depending upon the type of information desired, the data exchange systemmay access one or more of data repository 120, host system 102, andmanufacturing entities 140. Proof of product purchase may be requiredbefore enabling access to some of the information provided by the dataexchange system at step 206. For example, if the customer is a post-salecustomer, the data exchange system may automatically register thepurchased product with a warranty provider such as selling entity 104and/or manufacturing entity 140 using personal information provided bythe customer 115 at the time of sale. If the customer 115 is notauthorized to receive the requested information, the process ends atstep 212.

Once the requested information is found and the customer 115 isauthorized to receive it, the customer 115 may select a means oftransferring the information at step 208. For example, the informationmay be transferred via the customer's mobile computing device 110 usingwireless technology, e.g., Bluetooth™ or infrared. Alternatively, theinformation may be transmitted via email to the SOHO client system 118.The transfer of information may be immediate (e.g., while the customer115 is on the premises of selling entity 104. The transfer may takeplace via the Internet (e.g., exchanging URLs with generic materials(e.g., a user manual) or via email. The processes described in FIGS. 4and 6 provide additional details on the acquisition of accounting andwarranty information, respectively.

At step 210, the information is provided to the customer 115. Theinformation provided may include a unique identifier for identifying theproduct selected in other processes. Sample information provided to thecustomer 115 is shown generally in the table 300 of FIG. 3. In exemplaryembodiments, the table 300 is broken down by store (or selling entity)in column 302. The product 122 (or item) associated with each store 104is presented in column 304. The data exchange system lists each of thedocuments and information acquired for this product in column 306. Thepurchase price is listed in column 308. The STORE/OTHER CERTIFICATEcolumn 310 may reflect a certified agreement with the store orintermediate organization that may be used to certify discount ratesthat apply to the customer. This agreement may include an identifier forpresent and ongoing reference to the agreement. Also, table 300 includesa column 312 for updating the status of the product (e.g., whether it isstill owned by, and/or in the possession of, the customer). It will beappreciated that additional information (columns) may be provided andmanaged via the data exchange system.

As indicated above, accounting information may be acquired and organizedvia the data exchange system. Accounting information may includeinstructions for handling financial transactions and/or reporting.Accounting information may originate from government regulations and mayapply to specific products and/or product categories (e.g., luxury taxon yachts). An exemplary process for acquiring and managing accountinginformation will now be described with respect to the flow diagram ofFIG. 4. For purposes of illustration, it is assumed that the dataexchange system is in communication with an accounting package orsoftware 127 executing on SOHO client system 106. The process isinitiated at step 402 whereby information relating to a product ofinterest is loaded into the data exchange system application 130 (e.g.,specifications, pricing, rebates, etc.), as well as accounting rulesmade available from one or more third parties (e.g., selling entity 104,manufacturer(s) 140, host system 102, etc.) at step 404. Accountingrules are generally quite different from location to location.Accordingly, in exemplary embodiments, the data exchange systemautomatically identifies the location and the related accounting rulespertaining to the customer 115. This may be accomplished, e.g., byevaluating existing accounting information stored in SOHO client system106. In alternate embodiments, the customer 115 may proactively select alocation, if desired.

The accounting rules are presented to the SOHO client system 106 at step406. The rules may be altered via SOHO client system 106 as needed ordesired. In other words, the user at SOHO client system 106 need notaccept all of the accounting rules provided. The user may also provideinput regarding whether the product 122 is still owned by the businessof SOHO client system 106. A table 500 illustrating sample accountinginformation is provided in FIG. 5. The accounting information isorganized by location (e.g., country) using column 502. Locations may bedefined based upon areas where certain accounting instructions orregulations apply. For example, two locations, The Netherlands andBelgium, may be distinguished from each other in that they have uniqueaccounting rules; however, they may also be combined as one locationwhen the accounting rules to be applied concern regulations relating tothe European Union.

The product 122 (or item) is presented in column 504 and the purchaseprice is presented in column 506. As shown in table 500, the accountingrules for The Netherlands specifies that the depreciation regarding theproduct 122 (i.e., IBM® Thinkpad™ computer) be spread out over threeyears (see column 508). The user's financial program 127 will use theaccounting rules provided in Depreciation column 508 to handle thedepreciation function. It will be understood that other informationfields may be provided in table 500 as desired.

Once the accounting information is accepted, the accounting instructionsmay be loaded into the financial package 127 of SOHO client system 106at step 408. For instance, the investment of a computer is taken as costin the current year, but the depreciation is taken over a period ofthree years, according to the instructions received in the store 104that apply to the tax system in The Netherlands. Optionally, this stepmay load all available information into the financial package 127. Whenthe product is sold or discarded, the user may then be prompted toprovide details on any financial impact of the sale or loss. Details ofthis process are provided further in the flow diagram of FIG. 6.

Turning now to FIG. 6, a flow diagram of a process for managing warrantyinformation for a prospective claim via the data exchange system inexemplary embodiments will now be described. A user initiates theprocess at step 602 and locates the product 122 for which warranty isclaimed at step 604. Details about this product 122 have been stored inthe user's SOHO client system 106 as described above in FIG. 4.Alternatively, information may be scanned from the RFID tag 124 of theproduct 122 to obtain information. The data exchange system runs a checkto determine if the time span for which warranty can be claimed is stillvalid at step 606. This warranty information may be stored by one ormore of host system 102, manufacturer 140, and selling entity 104. Ifthe warranty is not within the specified time span, the data exchangesystem presents instructions and a disclaimer to the user at step 608and the process ends at step 618. The instructions may includeinformation as to the user's remaining options in light of theinvalidity determination (e.g., telephone number of a customer servicerepresentative associated with the warranty if the user believes thedetermination was made in error).

If, on the other hand, the product 122 is determined to be within thewarranty period at step 606, the data exchange system provides specificinformation about the terms and conditions of the warranty at step 610.As products often contain multiple variations on, for instance, types ofdamage covered, and therefore have different warranty clauses, the dataexchange system walks the user through a series of steps to determine ifthe user would be eligible for a warranty claim. This may be aninteractive process whereby the user is prompted to provide specificinformation regarding the condition and/or usage of the product 122. Atthe end of the process, however, the user may still be prompted with amessage that he/she might choose to consult the manufacturer or store ifwarranty applies.

Once instructed, the data exchange system determines whether a warrantymay be claimed at step 612. For example, a product (even though withinthe warranty period) may not be subject to warranty for failure to takethe specified precautions in its care and maintenance (e.g., a cellulartelephone is left outside in the rain and is damaged). If the warrantyis invalidated at step 612, the user is presented with instructions anda disclaimer at step 608 (as described above) and the process ends atstep 618. Otherwise, the process continues at step 614 whereby thewarranty information is relayed to the responsible party (e.g., sellingentity 104, manufacturer(s) 140) for processing. The data exchangesystem may also sets a reminder to follow up on the claim after adesignated period of time if no reply is received in order to ensurethat the claim is being timely processed at step 616. The process endsat step 618.

Turning now to FIG. 7, a flow diagram of a process for acquiring andmanaging net worth information via the data exchange system will now bedescribed. The process is initiated at step 702 via user input to, e.g.,data exchange system application 130 via host system 102. For example, auser at SOHO client system 106 accesses a web site of the host system102 using a login/password scheme whereby host system 102 maintainsrecords of the user's transactions. Alternatively, SOHO client system106 may executive a portion of the data exchange system application 130for obtaining net worth data relating to a product 122. The product ofinterest is located at step 704. At step 706, the net worth of theproduct is determined. Net worth may be calculated based upon theproduct information that was supplied when the product was purchased.Accounting instructions selected for the product (e.g., depreciationmethod selected) and the elapsed time since the date of purchase may beused to calculate the net worth. Alternatively, the data exchange systemmay acquire current market information available from an online resource(e.g., similar products posted for sale on eBay) in determining the networth. At step 708, the net worth determined in step 706 is comparedwith the actual historical accounting information. For example, theaccounting information may reflect a significant depreciation in theproduct due to, e.g., marketplace factors and growth in technologyrelated to the product. If the comparison reveals that the net worth andaccounting information are the same or similar for the product 122, theresults are presented to the user at step 712 and the process ends atstep 714. Otherwise, the data exchange system prompts the user withresults and enables the user to accept the differences or eliminate thedifferences by either compensating in the current accounting period orupdating the owner's financial package 127 with the information from theactual accounting records at step 710. The process then ends at step714.

The table 800 of FIG. 8 illustrates sample net worth data provided viathe data exchange system. A STORE column 802 provides the name oridentification of the store from which the product was purchased.DISCOUNT column 804 refers to the reduction in purchase price for theproduct or may include extra services a customer is eligible to receivein the store. The VALID THROUGH column 806 refers to a date in which thediscount offer expires. The CRITERIA column 808 provides informationregarding application of the discount (e.g., based upon the type ofproduct, direct or indirect agreement between the customer and theseller, etc.). These factors may be used to provide real-timeinformation within the store to the customer on an amount the customerwill pay for the product, taking into account any discounts.

The data exchange system of the present invention may reside on astand-alone computer system which may have access to the Internet, ormay reside on a computer system which is part of the network throughwhich there is Internet access. With a connection to a network and/orthe Internet, there are several different ways in which the processsoftware used to implement the systems and methods of the presentinvention may be integrated with the network, and deployed using a localnetwork, a remote network, an e-mail system, and/or a virtual privatenetwork. The following descriptions review the various ways ofaccomplishing these activities.

Integration of Data Exchange System Software. To implement the dataexchange systems and methods of the present invention, process software,which is composed of the software as described above and relatedcomponents including any needed data structures, is written and then ifdesired, integrated into a client, server, and network environment. Thisintegration is accomplished by taking those steps needed to enable theprocess software to coexist with other application, operating system andnetwork operating system software and then installing the processsoftware on the clients and servers in the environment where the processsoftware will function. An overview of this integration activity willnow be provided, followed by a more detailed description of the samewith reference to the flowcharts of FIGS. 9A and 9B.

The first step in the integration activity is to identify any softwareon the clients and servers where the process software will be deployedthat are required by the process software or that need to work inconjunction with the process software. This includes the networkoperating system, which is the software that enhances a basic operatingsystem by adding networking features.

Next, the software applications and version numbers are identified andcompared to the list of software applications and version numbers thathave been tested to work with the process software. Those softwareapplications that are missing or that do not match the correct versionare upgraded with the correct version numbers. Program instructions thatpass parameters from the process software to the software applicationswill be checked to ensure the parameter lists match the parameter listsrequired by the process software. Conversely, parameters passed by thesoftware applications to the process software will be checked to ensurethe parameters match the parameters required by the process software.The client and server operating systems including the network operatingsystems are identified and compared to the list of operating systems,version numbers, and network software that have been tested to work withthe process software. Those operating systems, version numbers, andnetwork software that do not match the list of tested operating systemsand version numbers are then upgraded on the clients and servers to therequired level.

After ensuring that the software resident on the computer systems wherethe process software is to be deployed is at the correct versionlevel(s), that is, has been tested to work with the process software,the integration is completed. This is done by installing the processsoftware on the clients and servers. Armed with the foregoing overviewof the integration activity, the following detailed description of thesame should be readily understood.

Referring to FIGS. 9A and 9B, step 900 begins the integration of theprocess software for implementing the search and reference systems andmethods of the present invention. It is determined whether there are anyprocess software programs that will execute on a server or servers atstep 902. If this is not the case, then integration proceeds todetermine if the process software will execute on clients at step 914.If there are process software programs that will execute on a server(s),then the server addresses are identified at step 904. The servers arechecked to see if they contain software that includes the operatingsystem (OS), applications, and network operating systems (NOS), togetherwith their version numbers, that have been tested with the processsoftware at step 906. The servers are also checked to determine if thereis any missing software that is required by the process software as partof the activity at step 906. A determination is made whether the versionnumbers match the version numbers of OS, applications and NOS that havebeen tested with the process software at step 908. If all of theversions match, and there is no missing required software, theintegration continues at step 914. If one or more of the version numbersdo not match, then the unmatched versions are updated on the server orservers with the correct versions at step 910. Additionally, if there ismissing required software, then it is updated on the server or serversat step 910. The server integration is completed by installing theprocess software at step 912.

Step 914, which follows either step 902, 908 or 912, determines if thereare any programs of the process software that will execute on theclients. If no process software programs execute on the clients, theintegration proceeds to step 920 and exits. If there are processsoftware programs that will execute on clients, the client addresses areidentified at step 916.

At step 918, the clients are checked to see if they contain softwarethat includes the operating system (OS), applications, and networkoperating systems (NOS) software, together with their version numbers,that have been tested with the process software. The clients are alsochecked at step 918 to determine if there is any missing software thatis required by the process software.

At step 922, a determination is made if the version numbers match theversion numbers of OS, applications and NOS that have been tested withthe process software. If all of the versions match, and there is nomissing required software, then the integration proceeds to step 920 andexits.

If one or more of the version numbers do not match, then the unmatchedversions are updated on the clients with the correct versions at step924. In addition, if there is missing required software, then it isupdated on the clients as part of step 924. The client integration iscompleted by installing the process software on the clients at step 926.The integration proceeds to step 920 and exits.

Deployment of Data Exchange System Software. It should be wellunderstood that the process software for implementing the data exchangesystem of the present invention may be deployed by manually loading theprocess software directly into the client, server, and proxy computersfrom a suitable storage medium such as a CD, DVD, etc. It is useful toprovide an overview of still other ways in which the process softwaremay also be automatically or semi-automatically deployed into one ormore computer systems. The process software may be deployed by sendingor loading the process software to a central server or a group ofcentral servers. From there, the process software may then be downloadedinto the client computers that will execute the process software.Alternatively, the process software may be sent directly to the clientsystem via e-mail. The process software is then either detached to adirectory or loaded into a directory by a button on the e-mail thatexecutes a program that detaches the process software attached to thee-mail into a directory. Another alternative is to send the processsoftware directly to a directory on the hard drive of a client computer.Also, when there are proxy servers, the automatic or self-automaticdeployment process will select the proxy server code, determine on whichcomputers to place the proxy servers' code, transmit the proxy servercode, and then install the proxy server code on the proxy computer. Theprocess software will be transmitted to the proxy server and then storedon the proxy server. Armed with this overview of the possible deploymentprocesses, the following detailed description of the same with referenceto FIGS. 10A and 10B, where the deployment processes are illustrated,will be more easily understood.

Step 1000 begins the deployment of the process software. It isdetermined whether there are any programs that will reside on a serveror servers when the process software is executed at step 1002. If theanswer is “yes”, then the servers that will contain the executables areidentified, as indicated in step 1036 in FIG. 10B. The process softwarefor the server or servers is transferred directly to the servers'storage via FTP or some other protocol or by copying though the use of ashared file system at step 1038. The process software is then installedon the servers as indicated at step 1040.

Next, as shown in step 1004 in FIG. 10A, a determination is made onwhether the process software is to be deployed by having users accessthe process software on a server or servers. If the users are to accessthe process software on servers, then the server addresses that willstore the process software are identified at step 1006.

Next, as shown at step 1018, a determination is made if a proxy serveris to be built to store the process software. A proxy server is a serverthat sits between a client application, such as a Web browser, and areal server. It intercepts all requests to the real server to see if itcan fulfill the requests itself. If not, it forwards the request to thereal server. The two primary benefits of a proxy server are to improveperformance and to filter requests. If a proxy server is required, thenthe proxy server is installed as indicated at step 1020. Next, theprocess software for implementing the present invention is sent to theservers, as indicated in step 1022 either via a protocol such as FTP orit is copied directly from the source files to the server files via filesharing. Another way of sending the process software to the servers isto send a transaction to the servers that contained the process softwareand have the server process the transaction. In this manner, the processsoftware may be received by and copied into the server's file system.Once the process software is stored at the servers, the users via theirclient computers, then access the process software on the servers andcopy it into to the file systems of their client computers at step 1024.Another alternative is to have the servers automatically copy theprocess software to each client and then run the installation programfor the process software at each client computer. Either way, the usercomputer executes or causes to be executed the program that installs theprocess software on the client computer at step 1042, then the processexits at step 1016.

Continuing now at step 1008 in FIG. 10A, a determination is made as towhether the process software is to be deployed by sending the processsoftware to users via e-mail. If the answer is yes, then, as indicatedat step 1010, the set of users where the process software will bedeployed are identified together with the addresses of the user clientcomputers. The process software is sent via e-mail in step 1026 (shownin FIG. 10B) to each of the users' client computers. Then, as indicatedin step 1028, the users receive the e-mail, and then detach the processsoftware from the e-mail to a directory on their client computers atstep 1030. The user then executes the program that installs the processsoftware on his client computer at step 1042, and then exits the processat step 1016.

Continuing at step 1012 (see bottom of FIG. 10A), a determination ismade on whether the process software will be sent directly to userdirectories on their client computers. If so, the user directories areidentified at step 1014. Then, the process software is transferreddirectly to the identified directory on the user's client computer, asindicated in step 1032. This can be done in several ways such as, butnot limited to, sharing of the file system directories and then copyingthem from the sender's file system to the recipient user's file systemor, alternatively, using a transfer protocol such as File TransferProtocol (FTP). Next, the users access the directories on their clientfile systems, as indicated in step 1034, in preparation for installingthe process software. Finally, the user executes the program thatinstalls the process software on his client computer at step 1042 andthen exits the process at step 1016.

Use of Virtual Private Networks for Data Exchange System Software. Theprocess software may be deployed, accessed and executed through the useof a virtual private network (VPN). A VPN is any combination oftechnologies that can be used to secure a connection through anotherwise unsecured or untrusted network. VPNs are used to improvesecurity and can often also reduce operational costs. The VPN makes useof a public network, usually the Internet, to connect remote sites orusers together. Instead of using a dedicated, real-world connection suchas a leased line, the VPN uses “virtual” connections routed through theInternet from the company's private network to the remote site oremployee(s). Access to the software via a VPN can be provided as aservice by specifically constructing the VPN for purposes of delivery orexecution of the process software (i.e., the software resideselsewhere). In such an instance, the lifetime of the VPN is oftenlimited to a given period of time or to a given number of deploymentsbased on an amount paid.

The process software may be deployed, accessed, and executed througheither a remote-access VPN or a site-to-site VPN. When using aremote-access VPN, the process software is typically deployed, accessed,and executed via the secure, encrypted connections between a company'sprivate network and remote users through a third-party service provider.The enterprise service provider (ESP) sets up and/or authorizes accessto a network access server (NAS) and provides the remote users withdesktop client software for their computers. The telecommuters can thendial a phone number (often a toll-free number) or attach directly via acable, DSL, or wireless modem to reach the NAS and use their VPN clientsoftware to access the corporate network and to access, download, andexecute the process software.

When using a site-to-site VPN, the process software is typicallydeployed, accessed and executed through the use of dedicated equipmentand large-scale encryption. These tools are often used to connectmultiple fixed sites of a larger company over a public network such asthe Internet.

The process software is transported over the VPN via a process calledtunneling. Tunneling is process involving the placing of an entirepacket within another packet and sending it over a network. The protocolof the outer packet is understood by the network and by both points,called tunnel interfaces, where the packet enters and exits the network.Tunneling generally encapsulates the private network data and protocolinformation within the public network transmissions so that the privatenetwork protocol information appears to the public network simply asunintelligible data. Armed with the foregoing overview of virtualprivate networks and how they operate and how they may be used totransport the process software, the following more detailed descriptionof same with reference to the flowcharts of FIGS. 11A-11C should be morereadily understood.

Step 1100 in FIG. 11A begins the virtual private network (VPN) process.A determination is made at step 1102 to see if a VPN for remote accessis required. If it is not required, then flow proceeds to step 1104. Ifit is required, then flow proceeds to step 1108 where a determination ismade as to whether a remote access VPN exists that is available for use.

If a remote access VPN does exist, then flow proceeds to step 1110 inFIG. 11A. Otherwise flow proceeds to step 1134 (see top of FIG. 11C),where a third party provider that will provide the secure, encryptedconnections between the company's private network and the company'sremote users is identified. Next, as indicated in step 1136, thecompany's remote users are identified. Then, at step 1138, theidentified third party provider then sets up a network access server(NAS). The NAS allows the remote users to dial a phone number (typicallya toll free number) or attach directly via a cable, DSL, wireless orother modem to access, download and install the desktop client softwarefor the remote-access VPN as indicated at step 1140.

Returning to step 1110 in FIG. 11A, after the remote access VPN has beenbuilt or if it been previously installed, the remote users can thenaccess the process software by dialing into the NAS or attachingdirectly via a cable, DSL, or other modem into the NAS. This step 1110allows entry into the corporate network, as indicated at step 1112,where the process software may be accessed. The process software istransported to the remote user's desktop computer over the network viatunneling. During tunneling, see step 1114, the process software isdivided into packets and each packet, including the data and protocolfor that packet, is placed within another packet. When the processsoftware arrives at the remote user's desktop computer, it is removedfrom the packets, reconstituted, and then may be executed on the remoteusers desktop, as indicated at step 1116.

Returning now to step 1104 in FIG. 11A, a determination is made to seeif a VPN for site-to-site access is required. If it is not required,then the process exits at step 1106. If it is required, flow proceeds tostep 1120 (see top of FIG. 11B) to determine if the site-to-site VPNexists. If it does exist, then flow proceeds to step 1126. If it doesnot exist, then as indicated at step 1122, dedicated equipment requiredto establish a site-to-site VPN is installed. Then the large-scaleencryption is built into the VPN at step 1124.

After the site-to-site VPN has been built or if it had been previouslyestablished, the users access the process software via the VPN asindicated in step 1126. Next, the process software is transported to thesite users over the network via tunneling as indicated in step 1128. Aspreviously explained, the process software is divided into packets andeach packet including the data and protocol is placed within anotherpacket, as indicated in step 1130. When the process software arrives atthe remote user's desktop, it is removed from the packets,reconstituted, and is executed on the site users desktop at step 1132.The process then proceeds to step 1106 and exits.

On Demand Computing for Data Exchange System Software. The processsoftware for implementing the data exchange system of the presentinvention may be shared; that is, it may be used to simultaneously servemultiple customers in a flexible, automated fashion. It is processsoftware that is easily standardized, requiring little customization,and it is scalable, thus providing capacity on demand in a pay-as-you-gomodel known as “on demand” computing. An overview of on demand computingas applied to the data exchange system software will now be provided,followed by a more detailed description of same made with reference tothe flowcharts of FIGS. 12A and 12B.

The process software for implementing the present invention can bestored on a shared file system accessible from one or more servers. Theprocess software may be executed via transactions that contain data andserver processing requests that use measurable CPU units on the accessedserver. CPU units are units of time such as minutes, seconds, and hourson the central processor of the server. Additionally, the accessedserver may make requests of other servers that require CPU units. CPUunits are an example that represents but one measurement of use. Othermeasurements of use include, but are not limited to, network bandwidth,memory usage, storage usage, packet transfers, complete transactions,etc.

When multiple customers use the same process software application, theirtransactions are differentiated by the parameters included in thetransactions that identify the unique customer and the type of servicefor that customer. All of the CPU units and other measurements of usethat are used for the services for each customer are recorded. When thenumber of transactions to any one server reaches a number that begins toaffect the performance of that server, other servers are accessed toincrease the capacity and to share the workload. Likewise, when othermeasurements of use such as network bandwidth, memory usage, storageusage, etc., approach a capacity so as to affect performance, additionalnetwork bandwidth, memory usage, storage etc. are added as needed toshare the workload.

The measurements of use used for each service and customer are sent to acollecting server that sums the measurements of use for each customerfor each service that was processed anywhere in the network of serversthat provide the shared execution of the process software. The summedmeasurements of use units are periodically multiplied by unit costs andthe resulting total process software application service costs arealternatively sent to the customer and or indicated on a web siteaccessed by the customer who then remits payment to the serviceprovider.

In another embodiment, the service provider requests payment directlyfrom a customer account at a banking or financial institution. In yetanother embodiment, if the service provider is also a customer of thecustomer that uses the process software application, the payment owed tothe service provider is reconciled to the payment owed by the serviceprovider to minimize the transfer of payments. Armed with the foregoingoverview, the detailed description of the on demand computing withrespect to the process software, and the following detailed descriptionof same with reference to FIGS. 12A and 12B where the on demandprocesses are illustrated, will be more easily understood.

Step 1200 begins the On Demand process. A transaction is created thatcontains the unique customer identification, the requested service typeand any service parameters that further specify the type of service asindicated in step 1202. The transaction is then sent to the main serveras shown in step 1204. In an On Demand environment, the main server mayinitially be the only server. Then, as capacity is consumed, otherservers are added to the On Demand environment.

The server central processing unit (CPU) capacities in the On Demandenvironment are queried at step 1206. The CPU requirement of thetransaction is estimated, then the servers' available CPU capacity inthe On Demand environment are compared to the transaction CPUrequirement to see if there is sufficient CPU available capacity in anyserver to process the transaction as indicated in step 1208. If there isnot sufficient server CPU available capacity, then additional server CPUcapacity is allocated to process the transaction as indicated in step1216. If there was already sufficient available CPU capacity, thetransaction is sent to a selected server at step 1210.

Before executing the transaction, a check is made of the remaining OnDemand environment to determine if the environment has sufficientavailable capacity for processing the transaction as indicated at step1212. This environment capacity consists of elements such as, but notlimited to, network bandwidth, processor memory, storage, etc. If thereis insufficient available capacity, then capacity will be added to theOn Demand environment as indicated in step 1214. Next the requiredsoftware to process the transaction is accessed, loaded into memory, andthe transaction is executed as indicated in step 1218.

The usage measurements are recorded as indicated in step 1220. The usagemeasurements consist of the portions of those functions in the On Demandenvironment that are used to process the transaction. The usage offunctions such as, but not limited to, network bandwidth, processormemory, storage and CPU cycles are what is recorded. The usagemeasurements are summed, multiplied by unit costs, and then recorded asa charge to the requesting customer as indicated in step 1222.

If the customer has requested that the On Demand costs be posted to aweb site as indicated in step 1224, then they are posted to a web siteat step 1226. If the customer has requested that the On Demand costs besent via e-mail to a customer address as indicated in step 1228, thenthey are sent to the customer via e-mail as indicated in step 1230. Ifthe customer has requested that the On Demand costs be paid directlyfrom a customer account at step 1232, then payment is received directlyfrom the customer account at step 1234. The On Demand process proceedsto step 1236 and then exits.

Exemplary embodiments of the present invention provide a variety ofuseful information regarding purchases at the point of sale or pre-saleperiod. Product specifications, pricing, taxes, manufacturer warrantyregistration and rebates, and other data are acquired from varioussources such as manufacturing enterprises, selling entities, financialinstitutions, etc.). Embodiments of the invention acquire, organize, andfacilitate dissemination of this information on behalf of individualconsumers and/or businesses. Accounting information, warranties, and networth are some of the information that is managed by the invention. Thisinformation may be transferred to designated parties in several manners,including e.g., wireless transfer to a mobile computing device, viaemail, web access, etc.

As described above, the embodiments of the invention may be embodied inthe form of computer-implemented processes and apparatuses forpracticing those processes. Embodiments of the invention may also beembodied in the form of computer program code containing instructionsembodied in tangible media, such as floppy diskettes, CD-ROMs, harddrives, or any other computer-readable storage medium, wherein, when thecomputer program code is loaded into and executed by a computer, thecomputer becomes an apparatus for practicing the invention. The presentinvention can also be embodied in the form of computer program code, forexample, whether stored in a storage medium, loaded into and/or executedby a computer, or transmitted over some transmission medium, such asover electrical wiring or cabling, through fiber optics, or viaelectromagnetic radiation, wherein, when the computer program code isloaded into and executed by a computer, the computer becomes anapparatus for practicing the invention. When implemented on ageneral-purpose microprocessor, the computer program code segmentsconfigure the microprocessor to create specific logic circuits.

While the invention has been described with reference to exemplaryembodiments, it will be understood by those skilled in the art thatvarious changes may be made and equivalents may be substituted forelements thereof without departing from the scope of the invention. Inaddition, many modifications may be made to adapt a particular situationor material to the teachings of the invention without departing from theessential scope thereof. Therefore, it is intended that the inventionnot be limited to the particular embodiment disclosed as the best modecontemplated for carrying out this invention, but that the inventionwill include all embodiments falling within the scope of the appendedclaims. Moreover, the use of the terms first, second, etc. do not denoteany order or importance, but rather the terms first, second, etc. areused to distinguish one element from another.

1. A method for implementing transaction-based data exchange updates byone or more computer processors in communication over a communicationnetwork, the method comprising: transferring, via a data exchange systemapplication executing on at least one of the computer processors,information relating to a product that is transferred via a transmissionmeans selected by an individual using one of the computer processors,the individual requesting the information, the information includingwarranty information, accounting depreciation instructions, pricinginformation, and product details; acquiring accounting instructions, theaccounting instructions originating from government regulation and basedon a geographic location of the individual, the acquiring based on atleast one of: automatically identifying the geographic location of theindividual; and evaluating existing accounting information, the existingaccounting information stored on a client system of the individual andaccessible by the data exchange system; calculating, by the one or morecomputer processors, a current net worth of the product, the current networth determined using; product information supplied at time ofpurchase, the product information including: product specifications;product identification information; warranty information; promotions;discounts; preferred customer pricing; and service information; and theaccounting instructions in combination with elapsed time since date ofpurchase, the accounting instructions comprising the accountinginstructions; comparing, by the data exchange system application,results of the calculating with historical accounting information, thehistorical accounting information including factors that are determinedto impact the current net worth, the factors including at least one of:depreciation due to market place factors; and changes in technologyrelated to the product; adjusting, by the data exchange systemapplication, the results of the calculating based on the comparing; andupdating, via the selected transmission means, a financial applicationof the computer processor associated with the individual, the financialapplication updated with the adjusted results of the calculating;providing results of the updating to the individual.
 2. The method ofclaim 1, further comprising: acquiring the information relating to aproduct from at least one of: a selling entity; a manufacturing entity;and a product catalog.
 3. The method of claim 1, wherein the warrantyinformation includes at least one of: terms and conditions; warrantyperiod; and product identification.
 4. The method of claim 1, whereinthe accounting rules include at least one of: depreciation rules; andtax rules.
 5. The method of claim 1, wherein the pricing informationincludes at least one of: retail price; price after discount; priceafter rebate; promotional price; and preferred customer price.
 6. Themethod of claim 1, wherein the product details include at least one of:product specifications; product model; and product images.
 7. The methodof claim 1, wherein the information is requested by the individual at aphysical point of sale.
 8. The method of claim 1, further comprisingdeploying process software for implementing said transaction-based dataexchange for an information management system, said deployingcomprising: installing said process software on at least one server;identifying server addresses for users accessing said process softwareon said at least one server; installing a proxy server if needed;sending said process software to said at least one server and copyingsaid process software to a file system of said at least one server;sending the process software to at least a first client computer; andexecuting said process software on said first client computer.
 9. Themethod of claim 8, wherein said installing said process software furthercomprises: determining if programs will reside on said at least oneserver when said process software is executed; identifying said at leastone server that will execute said process software; and transferringsaid process software to storage for said at least one server.
 10. Themethod of claim 8, wherein said sending said process software to saidfirst client computer further includes having said at least one serverautomatically copy said process software to said first client computer,and running an installation program at said first client computer toinstall said process software on said first client computer.
 11. Themethod of claim 8, wherein said sending said process software to saidfirst client computer further comprises identifying a user and anaddress of said first client computer.
 12. The method of claim 8,wherein said sending said process software to said first client computerincludes sending said process software to at least one directory on saidfirst client computer.
 13. The method of claim 8, wherein said sendingsaid process software to said first client computer includes sendingsaid process software to said first client computer via e-mail.
 14. Themethod of claim 1, further comprising integrating process software forimplementing said transaction-based data exchange for an informationmanagement system, said integrating comprising: determining if saidprocess software will execute on at least one server; identifying anaddress of said at least one server; checking said at least one serverfor operating systems, applications, and version numbers for validationwith said process software, and identifying any missing softwareapplications for said at least one server that are required forintegration; updating said at least one server with respect to anyoperating system and application that is not validated for said processsoftware, and providing any of said missing software applications forsaid at least one server required for said integration; identifyingclient addresses and checking client computers for operating systems,applications, and version numbers for validation with said processsoftware, and identifying any software applications missing from saidclient computers that are required for integration; updating said clientcomputers with respect to any operating system and application that isnot validated for said process software, and providing any missingsoftware application for said client computers required for saidintegration; and installing said process software on said clientcomputers and said at least one server.
 15. The method of claim 1,further comprising on-demand sharing of process software forimplementing said transaction-based data exchange for an informationmanagement system, said on demand sharing comprising: creating atransaction containing unique customer identification, requested servicetype, and service parameters; sending said transaction to at least onemain server; querying said at least one main server about processingcapacity associated with said at least one main server to help ensureavailability of adequate resources for processing of said transaction;and allocating additional processing capacity when additional capacityappears needed to process said transaction, said additional processingcapacity being selected from the group of additional capacitiesconsisting of central processing unit capacity, processor memorycapacity, network bandwidth capacity, and storage capacity.
 16. Themethod of claim 15, further comprising recording a plurality of usagemeasurements selected from the group of usage measurements consisting ofnetwork bandwidth, processor memory, storage, and central processingunit cycles.
 17. The method of claim 16, further comprising: summingsaid usage measurements acquiring at least one multiplicative valueassociated with said usage measurements and with unit costs; andrecording any such acquired multiplicative value as an on demand chargeto a requesting customer.
 18. The method of claim 17, further comprisingat least one of: posting said on demand charge on a web site ifrequested by said requesting customer; and sending said on demand chargevia e-mail to said requesting customer's e-mail address.
 19. The methodof claim 17, further comprising charging said on demand charge to saidrequesting customer's account if an account exists and if saidrequesting customer has selected a charge account payment method. 20.The method of claim 1, further comprising deploying, accessing, andexecuting process software for implementing said transaction-based dataexchange for an information management system, said deploying,accessing, and executing process software implemented through a virtualprivate network, the method further comprising: determining if a virtualprivate network is required; checking for remote access to said virtualprivate network when it is required; if said remote access does notexist, identifying a third party provider to provide secure, encryptedconnections between a private network and remote users; identifying saidremote users; and setting up a network access server operable fordownloading and installing client software on desktop computers forremote access of said virtual private network; accessing said processsoftware; transporting said process software to at least one remoteuser's desktop computer; and executing said process software on said atleast one remote user's desktop computer.
 21. The method of claim 20,further comprising: determining if said virtual private network has asite-to-site configuration for providing site-to-site access, and ifsaid virtual private network is not so available, installing equipmentrequired to establish a site-to-site configuration for said virtualprivate network; installing large scale encryption into saidsite-to-site virtual private network; and accessing said processsoftware through said site-to-site configuration with large scaleencryption.
 22. The method of claim 21, wherein said accessing saidprocess software further comprises at least one of: dialing into saidnetwork access server, and attaching directly via a modem into saidnetwork access server, said modem being selected from the group ofmodems consisting of telephone dial-up modems, cable modems, DSL modems,and wireless modems.
 23. The method of claim 1 further comprising:determining if the individual requesting the information is a post-salecustomer; determining if the individual requesting the information isauthorized to receive the information; and automatically registering thepurchased product with a warranty provider using personal informationprovided by the individual requesting the information when it isdetermined that the individual is a post-sale customer and is authorizedto receive the information.
 24. A storage medium encoded withmachine-readable program code for implementing transaction-based dataexchange, which when executed by the computer cause the computer toimplement a method, comprising: transferring, via a data exchange systemapplication executing on at least one of the computer processors,information relating to a product that is transferred via a transmissionmeans selected by an individual using one of the computer processors,the individual requesting the information, the information includingwarranty information, accounting depreciation instructions, pricinginformation, and product details; acquiring accounting instructions, theaccounting instructions originating from government regulation and basedon a geographic location of the individual, the acquiring based on atleast one of: automatically identifying the geographic location of theindividual; and evaluating existing accounting information, the existingaccounting information stored on a client system of the individual andaccessible by the data exchange system; calculating, by the one or morecomputer processors, a current net worth of the product, the current networth determined using: product information supplied at time ofpurchase, the product information including: product specifications;product identification information; warranty information; promotions;discounts; preferred customer pricing; and service information; and theaccounting instructions in combination with elapsed time since date ofpurchase, the accounting instructions comprising the accountinginstructions; comparing, by the data exchange system application,results of the calculating with historical accounting information, thehistorical accounting information including factors that are determinedto impact the current net worth, the factors including at least one of:depreciation due to market place factors; and changes in technologyrelated to the product; adjusting, by the data exchange systemapplication, the results of the calculating based on the comparing; andupdating, via the selected transmission means, a financial applicationof the computer processor associated with the individual, the financialapplication updated with the adjusted results of the calculating;providing results of the updating to the individual.
 25. The storagemedium of claim 24, further comprising instructions for causing thecomputer to implement: acquiring the information relating to a productfrom at least one of: a selling entity; a manufacturing entity; and aproduct catalog.
 26. The storage medium of claim 24, wherein thewarranty information includes at least one of: terms and conditions;warranty period; and product identification.
 27. The storage medium ofclaim 24, wherein the accounting rules include at least one of:depreciation rules; and tax rules.
 28. The storage medium of claim 24,wherein the pricing information includes at least one of: retail price;price after discount; price after rebate; promotional price; andpreferred customer price.
 29. The storage medium of claim 24, whereinthe product details include at least one of: product specifications;product model; and product images.
 30. The storage medium of claim 24,further comprising instructions for causing the computer to implementdeploying process software for implementing said transaction-based dataexchange for an information management system, said deployingcomprising: installing said process software on at least one server;identifying server addresses for users accessing said process softwareon said at least one server; installing a proxy server if needed;sending said process software to said at least one server and copyingsaid process software to a file system of said at least one server;sending the process software to at least a first client computer; andexecuting said process software on said first client computer.
 31. Thestorage medium of claim 30, wherein said installing said processsoftware further comprises: determining if programs will reside on saidat least one server when said process software is executed; identifyingsaid at least one server that will execute said process software; andtransferring said process software to storage for said at least oneserver.
 32. The storage medium of claim 30, wherein said sending saidprocess software to said first client computer further includes havingsaid at least one server automatically copy said process software tosaid first client computer, and running an installation program at saidfirst client computer to install said process software on said firstclient computer.
 33. The storage medium of claim 30, wherein saidsending said process software to said first client computer furthercomprises identifying a user and an address of said first clientcomputer.
 34. The storage medium of claim 30, wherein said sending saidprocess software to said first client computer includes sending saidprocess software to at least one directory on said first clientcomputer.
 35. The storage medium of claim 30, wherein said sending saidprocess software to said first client computer includes sending saidprocess software to said first client computer via e-mail.
 36. Thestorage medium of claim 24, further comprising instructions for causingthe computer to implement integrating process software for implementingsaid transaction-based data exchange for an information managementsystem, said integrating comprising: determining if said processsoftware will execute on at least one server; identifying an address ofsaid at least one server; checking said at least one server foroperating systems, applications, and version numbers for validation withsaid process software, and identifying any missing software applicationsfor said at least one server that are required for integration; updatingsaid at least one server with respect to any operating system andapplication that is not validated for said process software, andproviding any of said missing software applications for said at leastone server required for said integration; identifying client addressesand checking client computers for operating systems, applications, andversion numbers for validation with said process software, andidentifying any software applications missing from said client computersthat are required for integration; updating said client computers withrespect to any operating system and application that is not validatedfor said process software, and providing any missing softwareapplication for said client computers required for said integration; andinstalling said process software on said client computers and said atleast one server.
 37. The storage medium of claim 24, further comprisinginstructions for causing the computer to implement on-demand sharing ofprocess software for implementing said transaction-based data exchangefor an information management system, said on demand sharing comprising:creating a transaction containing unique customer identification,requested service type, and service parameters; sending said transactionto at least one main server; querying said at least one main serverabout processing capacity associated with said at least one main serverto help ensure availability of adequate resources for processing of saidtransaction; and allocating additional processing capacity whenadditional capacity appears needed to process said transaction, saidadditional processing capacity being selected from the group ofadditional capacities consisting of central processing unit capacity,processor memory capacity, network bandwidth capacity, and storagecapacity.
 38. The storage medium of claim 37, further comprisinginstructions for causing the computer to implement recording a pluralityof usage measurements selected from the group of usage measurementsconsisting of network bandwidth, processor memory, storage, and centralprocessing unit cycles.
 39. The storage medium of claim 38, furthercomprising instructions for causing the computer to implement: summingsaid usage measurements; acquiring at least one multiplicative valueassociated with said usage measurements and with unit costs; andrecording any such acquired multiplicative value as an on demand chargeto a requesting customer.
 40. The storage medium of claim 39, furthercomprising instructions for causing the computer to implement at leastone of: posting said on demand charge on a web site if requested by saidrequesting customer; and sending said on demand charge via e-mail tosaid requesting customer's e-mail address.
 41. The storage medium ofclaim 39, further comprising instructions for causing the computer toimplement charging said on demand charge to said requesting customer'saccount if an account exists and if said requesting customer hasselected a charge account payment method.
 42. The storage medium ofclaim 24, further comprising instructions for causing the computer toimplement deploying, accessing, and executing process software forimplementing said transaction-based data exchange for an informationmanagement system, said deploying, accessing, and executing processsoftware implemented through a virtual private network, the methodfurther comprising: determining if a virtual private network isrequired; checking for remote access to said virtual private networkwhen it is required; if said remote access does not exist, identifying athird party provider to provide secure, encrypted connections between aprivate network and remote users; identifying said remote users; andsetting up a network access server operable for downloading andinstalling client software on desktop computers for remote access ofsaid virtual private network; accessing said process software;transporting said process software to at least one remote user's desktopcomputer; and executing said process software on said at least oneremote user's desktop computer.
 43. The storage medium of claim 42,further comprising instructions for causing the computer to implement:determining if said virtual private network has a site-to-siteconfiguration for providing site-to-site access, and if said virtualprivate network is not so available, installing equipment required toestablish a site-to-site configuration for said virtual private network;installing large scale encryption into said site-to-site virtual privatenetwork; and accessing said process software through said site-to-siteconfiguration with large scale encryption.
 44. The storage medium ofclaim 43, wherein said accessing said process software further comprisesat least one of: dialing into said network access server, and attachingdirectly via a modem into said network access server, said modem beingselected from the group of modems consisting of telephone dial-upmodems, cable modems, DSL modems, and wireless modems.
 45. A system forimplementing transaction-based data exchange, comprising: a processorconfigured to execute a data exchange system application; and at leastone client system, the at least one client system connected to the dataexchange system over a network, the data exchange system applicationperforming a method comprising: transferring, via a data exchange systemapplication executing on at least one of the computer processors,information relating to a product that is transferred via a transmissionmeans selected by an individual using one of the computer processors,the individual requesting the information, the information includingwarranty information, accounting depreciation instructions, pricinginformation, and product details; acquiring accounting instructions, theaccounting instructions originating from government regulation and basedon a geographic location of the individual, the acquiring based on atleast one of: automatically identifying the geographic location of theindividual; and evaluating existing accounting information, the existingaccounting information stored on a client system of the individual andaccessible by the data exchange system; calculating, by the one or morecomputer processors, a current net worth of the product, the current networth determined using: product information supplied at time ofpurchase, the product information including: product specifications;product identification information; warranty information; promotions;discounts; preferred customer pricing; and service information; and theaccounting instructions in combination with elapsed time since date ofpurchase, the accounting instructions comprising the accountinginstructions; comparing, by the data exchange system application,results of the calculating with historical accounting information, thehistorical accounting information including factors that are determinedto impact the current net worth, the factors including at least one of:depreciation due to market place factors; and changes in technologyrelated to the product; adjusting, by the data exchange systemapplication, the results of the calculating based on the comparing; andupdating, via the selected transmission means, a financial applicationof the computer processor associated with the individual, the financialapplication updated with the adjusted results of the calculating;providing results of the updating to the individual.
 46. The system ofclaim 45, wherein the data exchange system application further performsacquiring the information relating to a product from at least one of: aselling entity; a manufacturing entity; and a product catalog.
 47. Thesystem of claim 45, wherein the warranty information includes at leastone of: terms and conditions; warranty period; and productidentification.
 48. The system of claim 45, wherein the accounting rulesinclude at least one of: depreciation rules; and tax rules.
 49. Thesystem of claim 45, wherein the pricing information includes at leastone of: retail price; price after discount; price after rebate;promotional price; and preferred customer price.
 50. The system of claim45, wherein the product details include at least one of: productspecifications; product model; and product images.
 51. The system ofclaim 45, wherein the information is requested by the individual at aphysical point of sale.